Info
- Utilizzare la checkbox di selezione a fianco di ciascun documento per attivare le funzionalità di stampa, invio email, download nei formati disponibili del (i) record.
Agile data warehousing project management [[electronic resource] ] : business intelligence systems using Scrum / / Ralph Hughes
| Agile data warehousing project management [[electronic resource] ] : business intelligence systems using Scrum / / Ralph Hughes |
| Autore | Hughes Ralph <1959-> |
| Edizione | [1st ed.] |
| Pubbl/distr/stampa | Waltham, MA, : Morgan Kaufmann, 2013 |
| Descrizione fisica | 1 online resource (379 p.) |
| Disciplina | 005.74/5 |
| Soggetto topico |
Agile software development
Business intelligence - Data processing Data warehousing Project management |
| ISBN |
1-283-60983-5
9786613922281 0-12-396517-9 |
| Formato | Materiale a stampa  |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Front Cover; Agile Data Warehousing Project Management; Copyright Page; Contents; List of Figures; List of Tables; Preface; Answering the skeptics; Intended audience; Parts and chapters of the book; Invitation to join the agile warehousing community; Author's Bio; 1: An Introduction to Iterative Development; 1 What Is Agile Data Warehousing?; A quick peek at an agile method; The "disappointment cycle" of many traditional projects; The waterfall method was, in fact, a mistake; Agile's iterative and incremental delivery alternative; Agile as an answer to waterfall's problems
Increments of small scopeBusiness centric; Colocation; Self-organized teams; Just in time; 80-20 Specifications; Fail fast and fix quickly; Integrated quality assurance; Agile methods provide better results; Agile for data warehousing; Data warehousing entails a "breadth of complexity"; Adapted scrum handles the breadth of data warehousing well; Managing data warehousing's "depth of complexity"; Guide to this book and other materials; Simplified treatment of data architecture for book 1; Companion web site; Where to be cautious with agile data warehousing; Summary 2 Iterative Development in a NutshellStarter concepts; Three nested cycles; The release cycle; Development and daily cycles; Shippable code and the definition of done; Time-boxed development; Caves and commons; Product owners and scrum masters; Product owner; Scrum master; Developers as "generalizing specialists"; Improved role for the project manager; Might a project manager serve as a scrum master?; User stories and backlogs; Estimating user stories in story points; Iteration phase 1: story conferences; Iteration phase 2: task planning Basis of estimate cards to escape repeating hard thinkingTask planning doublechecks story planning; Iteration phase 3: development phase; Self-organization; Daily scrums; Accelerated programming; Test-driven development; Architectural compliance and "tech debt"; Iteration phase 4: user demo; Iteration phase 5: sprint retrospectives; Retrospectives are vital; Close collaboration is essential; Selecting the optimal iteration length; Nonstandard sprints; Sprint 0; Architectural sprints; Implementation sprints; "Spikes"; "Hardening" sprints; Where did scrum come from?; Distant history Scrum emergesSummary; 3 Streamlining Project Management; Highly transparent task boards; Task boards amplify project quality; Task boards naturally integrate team efforts; Scrum masters must monitor the task board; Burndown charts reveal the team aggregate progress; Detecting trouble with burndown charts; Developers are not the burndown chart's victims; Calculating velocity from burndown charts; Common variations on burndown charts; Setting capacity when the team delivers early; Managing tech debt; Managing miditeration scope creep; Diagnosing problems with burndown chart patterns An early hill to climb |
| Record Nr. | UNINA-9910785504103321 |
Hughes Ralph <1959->
|
||
| Waltham, MA, : Morgan Kaufmann, 2013 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Agile data warehousing project management [[electronic resource] ] : business intelligence systems using Scrum / / Ralph Hughes
| Agile data warehousing project management [[electronic resource] ] : business intelligence systems using Scrum / / Ralph Hughes |
| Autore | Hughes Ralph <1959-> |
| Edizione | [1st ed.] |
| Pubbl/distr/stampa | Waltham, MA, : Morgan Kaufmann, 2013 |
| Descrizione fisica | 1 online resource (379 p.) |
| Disciplina | 005.74/5 |
| Soggetto topico |
Agile software development
Business intelligence - Data processing Data warehousing Project management |
| ISBN |
1-283-60983-5
9786613922281 0-12-396517-9 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Front Cover; Agile Data Warehousing Project Management; Copyright Page; Contents; List of Figures; List of Tables; Preface; Answering the skeptics; Intended audience; Parts and chapters of the book; Invitation to join the agile warehousing community; Author's Bio; 1: An Introduction to Iterative Development; 1 What Is Agile Data Warehousing?; A quick peek at an agile method; The "disappointment cycle" of many traditional projects; The waterfall method was, in fact, a mistake; Agile's iterative and incremental delivery alternative; Agile as an answer to waterfall's problems
Increments of small scopeBusiness centric; Colocation; Self-organized teams; Just in time; 80-20 Specifications; Fail fast and fix quickly; Integrated quality assurance; Agile methods provide better results; Agile for data warehousing; Data warehousing entails a "breadth of complexity"; Adapted scrum handles the breadth of data warehousing well; Managing data warehousing's "depth of complexity"; Guide to this book and other materials; Simplified treatment of data architecture for book 1; Companion web site; Where to be cautious with agile data warehousing; Summary 2 Iterative Development in a NutshellStarter concepts; Three nested cycles; The release cycle; Development and daily cycles; Shippable code and the definition of done; Time-boxed development; Caves and commons; Product owners and scrum masters; Product owner; Scrum master; Developers as "generalizing specialists"; Improved role for the project manager; Might a project manager serve as a scrum master?; User stories and backlogs; Estimating user stories in story points; Iteration phase 1: story conferences; Iteration phase 2: task planning Basis of estimate cards to escape repeating hard thinkingTask planning doublechecks story planning; Iteration phase 3: development phase; Self-organization; Daily scrums; Accelerated programming; Test-driven development; Architectural compliance and "tech debt"; Iteration phase 4: user demo; Iteration phase 5: sprint retrospectives; Retrospectives are vital; Close collaboration is essential; Selecting the optimal iteration length; Nonstandard sprints; Sprint 0; Architectural sprints; Implementation sprints; "Spikes"; "Hardening" sprints; Where did scrum come from?; Distant history Scrum emergesSummary; 3 Streamlining Project Management; Highly transparent task boards; Task boards amplify project quality; Task boards naturally integrate team efforts; Scrum masters must monitor the task board; Burndown charts reveal the team aggregate progress; Detecting trouble with burndown charts; Developers are not the burndown chart's victims; Calculating velocity from burndown charts; Common variations on burndown charts; Setting capacity when the team delivers early; Managing tech debt; Managing miditeration scope creep; Diagnosing problems with burndown chart patterns An early hill to climb |
| Record Nr. | UNINA-9910825750903321 |
|
Hughes Ralph <1959->
|
||
| Waltham, MA, : Morgan Kaufmann, 2013 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||
Agile data warehousing project management [[electronic resource] ] : business intelligence systems using Scrum / / Ralph Hughes
| Agile data warehousing project management [[electronic resource] ] : business intelligence systems using Scrum / / Ralph Hughes |
| Autore | Hughes Ralph <1959-> |
| Edizione | [1st ed.] |
| Pubbl/distr/stampa | Amsterdam ; ; Boston, : Elsevier / MK, 2012 |
| Descrizione fisica | 1 online resource (379 p.) |
| Disciplina | 005.74/5 |
| Soggetto topico |
Agile software development
Business intelligence - Data processing Data warehousing Project management |
| Soggetto genere / forma | Electronic books. |
| ISBN |
1-283-60983-5
9786613922281 0-12-396517-9 |
| Formato | Materiale a stampa |
| Livello bibliografico | Monografia |
| Lingua di pubblicazione | eng |
| Nota di contenuto |
Front Cover; Agile Data Warehousing Project Management; Copyright Page; Contents; List of Figures; List of Tables; Preface; Answering the skeptics; Intended audience; Parts and chapters of the book; Invitation to join the agile warehousing community; Author's Bio; 1: An Introduction to Iterative Development; 1 What Is Agile Data Warehousing?; A quick peek at an agile method; The "disappointment cycle" of many traditional projects; The waterfall method was, in fact, a mistake; Agile's iterative and incremental delivery alternative; Agile as an answer to waterfall's problems
Increments of small scopeBusiness centric; Colocation; Self-organized teams; Just in time; 80-20 Specifications; Fail fast and fix quickly; Integrated quality assurance; Agile methods provide better results; Agile for data warehousing; Data warehousing entails a "breadth of complexity"; Adapted scrum handles the breadth of data warehousing well; Managing data warehousing's "depth of complexity"; Guide to this book and other materials; Simplified treatment of data architecture for book 1; Companion web site; Where to be cautious with agile data warehousing; Summary 2 Iterative Development in a NutshellStarter concepts; Three nested cycles; The release cycle; Development and daily cycles; Shippable code and the definition of done; Time-boxed development; Caves and commons; Product owners and scrum masters; Product owner; Scrum master; Developers as "generalizing specialists"; Improved role for the project manager; Might a project manager serve as a scrum master?; User stories and backlogs; Estimating user stories in story points; Iteration phase 1: story conferences; Iteration phase 2: task planning Basis of estimate cards to escape repeating hard thinkingTask planning doublechecks story planning; Iteration phase 3: development phase; Self-organization; Daily scrums; Accelerated programming; Test-driven development; Architectural compliance and "tech debt"; Iteration phase 4: user demo; Iteration phase 5: sprint retrospectives; Retrospectives are vital; Close collaboration is essential; Selecting the optimal iteration length; Nonstandard sprints; Sprint 0; Architectural sprints; Implementation sprints; "Spikes"; "Hardening" sprints; Where did scrum come from?; Distant history Scrum emergesSummary; 3 Streamlining Project Management; Highly transparent task boards; Task boards amplify project quality; Task boards naturally integrate team efforts; Scrum masters must monitor the task board; Burndown charts reveal the team aggregate progress; Detecting trouble with burndown charts; Developers are not the burndown chart's victims; Calculating velocity from burndown charts; Common variations on burndown charts; Setting capacity when the team delivers early; Managing tech debt; Managing miditeration scope creep; Diagnosing problems with burndown chart patterns An early hill to climb |
| Record Nr. | UNINA-9910462367503321 |
|
Hughes Ralph <1959->
|
||
| Amsterdam ; ; Boston, : Elsevier / MK, 2012 | ||
| Materiale a stampa | ||
| Lo trovi qui: Univ. Federico II | ||
| ||